Knowledge Overview

BindAI V1 Knowledge makes project reference information available to Agents during workflow execution. The verified V1 flow is:

Project Knowledge
      |
      v
Configured Agent
      |
      v
Knowledge search
      |
      v
Relevant information
      |
      v
Model

Knowledge is configured for an Agent and is used during Agent execution.

What is Knowledge?

Knowledge provides reference information that an Agent may need while processing a request. Typical uses include:

Product information
Support information
Project documentation
Internal guides
Application-specific reference material

Knowledge is different from workflow state and Memory:

Knowledge
    |
    +-- Project reference information


Memory
    |
    +-- Persistent Agent conversation context


Workflow state
    |
    +-- Current workflow execution

Knowledge in V1

A project can contain Knowledge documents that are available to Agents. For example:

my-project/
├── agents/
├── workflows/
├── tools/
└── knowledge/
    └── knowledge-test.md

An Agent can be configured with a Knowledge entry:

Agent
 |
 +-- Model
 +-- Instructions
 +-- Knowledge: knowledge-test
 +-- Memory: support-memory

When the Agent executes, the configured Knowledge is searched and relevant information can be used as part of the Agent’s context.

Knowledge and Agents

Knowledge is integrated into Agent execution. The basic flow is:

Workflow
    |
    v
Agent
    |
    +----> Configured Knowledge
    |             |
    |             v
    |        Relevant information
    |
    v
Model
    |
    v
Agent result

The workflow does not need a separate Knowledge node to use project Knowledge. The Agent’s Knowledge configuration determines which Knowledge is available during execution.

Concrete V1 Example

A verified V1 Knowledge example uses:

knowledge/
└── knowledge-test.md

The document contains:

ORANGE-PENGUIN-742

The Agent is configured with:

Knowledge: knowledge-test

A request can then be processed through the Agent with a question related to the configured Knowledge. The Knowledge runtime searches the configured project Knowledge and makes relevant information available to the Agent. For this example, the Agent can retrieve information containing:

ORANGE-PENGUIN-742

This verifies the complete V1 path:

Project document
      |
      v
Knowledge configuration
      |
      v
Agent execution
      |
      v
Knowledge search
      |
      v
Relevant content

Two-Run Example

Knowledge remains project-level information, so it can be used across separate workflow executions.

Run 1

Workflow Run 1
      |
      v
Agent
      |
      v
Knowledge: knowledge-test
      |
      v
ORANGE-PENGUIN-742

The Agent can use the configured Knowledge during the first execution.

Run 2

Workflow Run 2
      |
      v
Agent
      |
      v
Knowledge: knowledge-test
      |
      v
ORANGE-PENGUIN-742

The same project Knowledge remains available to the second execution. Knowledge therefore belongs to the project rather than to a single workflow instance.

Knowledge in Studio

BindAI Studio provides Knowledge configuration as part of Agent configuration. An Agent can select a project Knowledge entry:

Agent Configuration

Model
Instructions
Knowledge
Memory

The selected Knowledge becomes part of the Agent’s runtime configuration. This allows Knowledge to be configured independently of the workflow graph.

Knowledge and Memory

Knowledge and Memory have different responsibilities.

Knowledge	Memory
Project reference information	Persistent Agent conversation context
Knowledge documents	Previous Agent conversation
Searched during Agent execution	Loaded and saved as conversation context
Configured for Agent use	Configured by memory name
Project-level information	SQLite-backed project memory

For example:

Knowledge
    |
    +-- Product documentation


Memory
    |
    +-- Previous customer conversation

An Agent can use both during the same execution.

Knowledge and Workflow State

Knowledge is separate from workflow state. Workflow state belongs to a particular workflow execution:

Workflow State
    |
    +-- input
    +-- agent_output
    +-- tool_output
    +-- execution state
    +-- human-task state

Knowledge contains project reference information used during Agent execution. A workflow variable should not be treated as a replacement for project Knowledge.

Knowledge and Tools

Knowledge and Tools have different purposes. A Tool performs an operation:

Agent
  |
  v
Tool
  |
  v
Operation

Knowledge provides reference information:

Agent
  |
  v
Knowledge
  |
  v
Reference information

An Agent can use both. For example, an Agent can use project information from Knowledge and then pass its result to a Tool.

Knowledge in Workflows

Knowledge participates in workflows through Agent nodes. For example:

Start
  |
  v
Agent
  |
  v
Tool
  |
  v
End

The Agent can use its configured Knowledge during execution. The Tool can then receive the Agent’s output through normal workflow variable mapping. No separate Knowledge node is required.

Knowledge and Conditions

Knowledge can be used before a Condition:

Start
  |
  v
Agent
  |
  v
Condition
  |
  +---- true ----> Tool
  |
  +---- false ---> Human Task

The Agent can use Knowledge to produce information used by later workflow nodes. The Condition controls workflow routing. These are separate responsibilities.

Knowledge and Human Tasks

Knowledge can be used before a Human Task:

Start
  |
  v
Agent
  |
  v
Human Task
  |
  v
End

The Agent uses project Knowledge during its execution. The Human Task controls the workflow’s waiting and approval state.

Knowledge and Parallel Execution

Knowledge can be used by Agents in parallel branches:

             +---- Agent A ----+
             |                 |
Start -------+                 +---- Join
             |                 |
             +---- Agent B ----+

Each Agent uses the Knowledge configured for that Agent. Parallel and Join control workflow execution and synchronization.

Knowledge and Loops

A Knowledge-enabled Agent can participate in a workflow containing a Loop:

Start
  |
  v
Loop
  |
  v
Agent
  |
  v
End

The Loop controls repeated workflow execution. Knowledge provides reference information to the Agent.

Knowledge and Connections

Knowledge can be combined with the V1 Webhook connection capability:

Start
  |
  v
Agent
  |
  +-- Knowledge
  |
  v
Webhook Tool
  |
  v
End

The Agent uses Knowledge for reference information. The connection-backed Tool performs the external Webhook operation. This combines project information with an external action in the same workflow.

Knowledge Documents

V1 Knowledge is project-local and document-oriented. A project can contain Knowledge content such as:

knowledge/
├── product-guide.md
├── support-guide.md
└── company-policy.md

The important V1 behavior is that configured project Knowledge can be searched during Agent execution. This page intentionally does not describe additional document ingestion, parsing, chunking, embedding, or indexing systems that are not part of the verified Studio V1 workflow.

Knowledge Retrieval

The verified V1 retrieval flow is:

Agent request
    |
    v
Configured Knowledge
    |
    v
Knowledge search
    |
    v
Relevant information
    |
    v
Agent context
    |
    v
Model execution

For example:

knowledge-test
      |
      v
knowledge-test.md
      |
      v
ORANGE-PENGUIN-742
      |
      v
Agent

The application does not need to manually copy the Knowledge document into every workflow input.

Knowledge Persistence

Knowledge belongs to the project. A workflow run can finish while the project’s Knowledge remains available to later workflow runs:

Project
   |
   +-- Knowledge
   |
   +-- Agents
   |
   +-- Workflows

This differs from workflow-instance state, which belongs to a particular execution.

Knowledge Configuration With Memory

An Agent can use both Knowledge and Memory:

Agent
 |
 +-- Model
 |
 +-- Instructions
 |
 +-- Knowledge: knowledge-test
 |
 +-- Memory: support-memory

During execution:

Agent
 |
 +---- Knowledge
 |
 +---- Memory
 |
 +---- Workflow input
 |
 v
Model

Knowledge provides project reference information. Memory provides persistent conversation context.

Knowledge Quality

Knowledge quality depends on the information provided to the Agent. Good Knowledge content should be:

Relevant to the Agent’s purpose
Clear and consistent
Kept up to date
Organized around information the Agent needs
Limited to useful project reference material

Avoid adding unrelated content to an Agent’s Knowledge configuration.

Testing Knowledge

A useful V1 test should verify Agent behavior rather than only checking that a document exists. A basic test is:

Create project Knowledge.
Add Knowledge content.
Configure an Agent to use the Knowledge.
Run the Agent through a workflow.
Ask about information contained in the Knowledge.
Verify that the Agent can use the configured Knowledge.

The verified example is:

Knowledge:
    knowledge-test

Document:
    knowledge-test.md

Content:
    ORANGE-PENGUIN-742

The Agent can retrieve and use this Knowledge during execution.

Knowledge With Memory

Knowledge and Memory can be used together:

Run 1
  |
  +-- Knowledge provides project information
  |
  +-- Memory stores conversation context


Run 2
  |
  +-- Knowledge remains available
  |
  +-- Memory loads previous conversation context

The two systems solve different problems and can therefore be used together by the same Agent.

Current V1 Scope

Capability	V1
Project Knowledge	✅
Knowledge documents	✅
Agent Knowledge configuration	✅
Knowledge search during Agent execution	✅
Knowledge through Studio	✅
Knowledge with Memory	✅
Knowledge with Tools	✅
Knowledge with Conditions	✅
Knowledge with Loops	✅
Knowledge with Parallel/Join	✅
Knowledge with Human Tasks	✅
Knowledge with Webhook-backed Tools	✅
Advanced embedding administration	❌
Advanced vector-store administration	❌
BM25 configuration	❌
Hybrid retrieval configuration	❌
Reranker configuration	❌
Advanced RAG pipeline administration	❌
MCP Knowledge integration	❌

Summary

BindAI V1 Knowledge provides project reference information that configured Agents can search and use during workflow execution. The practical V1 architecture is:

Project Knowledge
      |
      v
Configured Agent
      |
      +---- Knowledge search
      |
      +---- Memory
      |
      +---- Workflow input
      |
      v
Model
      |
      v
Workflow Result

The responsibilities remain separate:

Knowledge provides project reference information.
Memory provides persistent Agent conversation context.
Workflow state tracks the current workflow execution.
Tools perform operations.

The V1 Knowledge implementation focuses on project-local Knowledge used by Agents through Studio and the runtime. Advanced embedding management, vector-store administration, configurable retrieval strategies, reranking, and custom RAG administration are outside the verified V1 scope.

Getting Started

Core

Tools

Memory

Knowledge

Workflows

Projects

Templates

Connections

API Reference

Automation

Roadmap

05.1 overview

Knowledge Overview

What is Knowledge?

Knowledge in V1

Knowledge and Agents

Concrete V1 Example

Two-Run Example

Run 1

Run 2

Knowledge in Studio

Knowledge and Memory

Knowledge and Workflow State

Knowledge and Tools

Knowledge in Workflows

Knowledge and Conditions

Knowledge and Human Tasks

Knowledge and Parallel Execution

Knowledge and Loops

Knowledge and Connections

Knowledge Documents

Knowledge Retrieval

Knowledge Persistence

Knowledge Configuration With Memory

Knowledge Quality

Testing Knowledge

Knowledge With Memory

Current V1 Scope

Summary

​Knowledge Overview

​What is Knowledge?

​Knowledge in V1

​Knowledge and Agents

​Concrete V1 Example

​Two-Run Example

​Run 1

​Run 2

​Knowledge in Studio

​Knowledge and Memory

​Knowledge and Workflow State

​Knowledge and Tools

​Knowledge in Workflows

​Knowledge and Conditions

​Knowledge and Human Tasks

​Knowledge and Parallel Execution

​Knowledge and Loops

​Knowledge and Connections

​Knowledge Documents

​Knowledge Retrieval

​Knowledge Persistence

​Knowledge Configuration With Memory

​Knowledge Quality

​Testing Knowledge

​Knowledge With Memory

​Current V1 Scope

​Summary

Knowledge Overview

What is Knowledge?

Knowledge in V1

Knowledge and Agents

Concrete V1 Example

Two-Run Example

Run 1

Run 2

Knowledge in Studio

Knowledge and Memory

Knowledge and Workflow State

Knowledge and Tools

Knowledge in Workflows

Knowledge and Conditions

Knowledge and Human Tasks

Knowledge and Parallel Execution

Knowledge and Loops

Knowledge and Connections

Knowledge Documents

Knowledge Retrieval

Knowledge Persistence

Knowledge Configuration With Memory

Knowledge Quality

Testing Knowledge

Knowledge With Memory

Current V1 Scope

Summary